<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
      "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
  <title>Using LADOSC</title>
  <meta name="generator" content="Amaya 9.54, see http://www.w3.org/Amaya/" />
  <link href="using-ladosc-files/ingen-large.png" />
</head>

<body style="background-color: Grey;">
<h1>ladosc communication plugins</h1>
<p>Before I started using Linux, I used a windows audio application called
<a href="http://www.audiomulch.com/">audiomulch</a>, by Ross Bencina. One thing
I have missed, since I stopped using closed source software, is the way that
audiomulch could automate plugin parameters on a timeline:</p>
<a href="http://www.audiomulch.com/static/screenshot1.htm">
<img
   alt="using the plugin automator in audiomulch"
   src="http://www.audiomulch.com/images/screenshot1_thumb.jpg"
   />
</a>
<p>By now, maybe, someone has made a linux application with that functionality.
lmms, beast, blue, pd, and cecilia come close. But, as I got to know linux
better, I realized that the "single big app that does everything" approach to
audio is counterproductive. I think that there are at least 100 sound file
editors available for linux. Projects come and go daily. Everything lives or
dies by its features. Not wanting to waste my time, or force anyone to duplicate
my effort, I present to you: ladosc.</p>
<p>Ladosc uses OSC differently than most applications do. Most applications use
OSC as a networked version of MIDI. Ladosc is flexible, but is primarily
designed for sending control signals (think envelope values, continuous pitch
bends, automated knob twiddling).</p>

<h2>What is LADOSC?</h2>

<p>Ladosc is a pair of LADSPA plugins, which allow a pair of Linux Audio
Developers' Simple Plugin Architecture host applications to communicate via
the Open Sound Control protocol.</p>


<h2>What does LADOSC look like?</h2>

<p>LADOSC looks like however the host application decides to display
<a href="screenshots.html">it</a>.</p>
<h2>How does LADOSC work?</h2>
<p>Here is a detailed breakdown of the plugins, and their parameters, and their
behaviour: <a href="specification.html">Ladosc Specification</a></p>
<h2>I don't quite understand that, how do I use LADOSC?</h2>
<p>Ladosc is implemented as two plugins: osc_out and osc_in.
  Here is a step by step <a href="tutorial.html">tutorial</a> of their
  usage.</p>
<h2>That was still too complicated, do you have a simple, step by step,
  beginner's introduction?</h2>
Yes, here it is, I hope you like it: <a href="step_by_step.html">The super
simple step by step guide to using ladosc, with plenty of pictures</a>.
</body>
</html>
